I'm migrating from SBS2003 SP2 to SBS2011 Standard. I just finished moving Exchange mailboxes to the new server, successfully. To test, I started my Outlook 2003 (old, I know) and sent a test message to my MSN mail. The msg stayed in my Outbox. I clicked Send/Receive and got: "Task 'MS Exchange Server' reported error (0x8004011D): 'The server is not available. Contact your administrator if this condition persists." That is followed immediately by: "Task 'MS Exchange Server - Sending' reported error (0x80040115): 'The connection to the MS Exchange Server is unavailable.....' I tried another user's Outlook 2010, same result, plus Outlook prompts for logon credentials. If I create a new profile in either version of Outlook, it sees the server, but won't open "this set of folders". I have noticed that on the old Exchange 2003 server, in the Exchange System Manager under First Routing Group/Members, the only member is the old server and it is the master. I don't know if that matters. I have rebooted both my Windows XP workstation and the SBS2011 server. I followed, step-by-step, the instructions in "Migrate to Windows SBS 2011 Standard from Windows SBS 2003". It's 12:21 a.m. and customers are going to expect their email to work at 08:00. I need help very badly. Thanks in advance, -J

This might help you narrow down the problem: After starting Outlook on a client, hold Ctrl and right click the Outlook icon in the System tray, and click Connection status. In the list of connections, you should be able to see which of the server connections is unavailable. Hope this helps.

Thanks, heppp, for the recommendation. I tried what you suggested from an XP machine running OL 2003. It shows I'm connected to the new server, Type is Directory, Connection is IP, Status is Established, Req/Fail is 5/0 (I've reconnected a few times), Avg Resp is 9. There are actually two lines in the Connection Status results, both to the new server. They are identical, except the 2nd one has Avg Resp of 62. I checked Connection Status on a Win7 machine running OL 2010, it showed as being connected to the OLD server, which is way wrong. We are unable to send email internally. I'm actually a desktop support guy, not a server guy, so I have no previous Exchange knowledge on which to fly. Any help I can get from those more experienced is GREATLY appreciated. Thanks,-J

I found this TechNet post: http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/cd0e0c69-108d-4394-b3ba-4f586dca49b1, "Exchange 2010 Users Cannot Expand Public Folders". I checked and we had the same problem on our new server, we couldn't expand public folders. The post talks about RPC problems and the need to set a static port for public folder connections: "To set a static port for public folder connections, follow the same steps you carried out for changing the TCP/IP port used for the RPC CA service." I started investigating that angle and found the Microsoft Exchange RPC Client Access service, set to Automatic, was not running on our new server. I started it and then could expand public folders from my OL. Also, the two test msgs in my outbox were sent immediately. I had one customer test his OL 2010, he was able to send/receive. I then rebooted the server and checked the RPC Client svc. It did not start again and I couldn't send an email message. Started the service manually, re-started OL, messages send ok. So, the problem appears to be the Exchange RPC Client Access service not starting. I also notice that 3 other Exchange services, all set to automatic, are not loading: Exch System Attendant, Exch Forms-Based Authentication, and Exch EdgeSync. Questions: What would stop Exch RPC Client Access from starting automatically? What would stop the other Exchange services from starting automatically, and do I need to worry about each them? Thanks again,-J

Hi, For the sake of resoving your problem effectively, you'd better put SBS related issue to SBS support forum. Here's the link for you: http://social.technet.microsoft.com/Forums/en-US/category/sbsserver Thanks. Rowen TechNet Community Support

Hi, For the sake of resoving your problem effectively, you'd better put SBS related issue to SBS support forum. Here's the link for you: http://social.technet.microsoft.com/Forums/en-US/category/sbsserver Thanks. Rowen TechNet Community Support